|
Bus monitoring is a term used in flight testing when capturing data from avionics buses and networks in data acquisition telemetry systems. Commonly monitored avionics buses include * ARINC Standard buses such as ARINC-429,〔(【引用サイトリンク】title=ARINC 429 Tutorial )〕 ARINC 573, ARINC 717 * ARINC 629 also known as Multi-transmitter Data Bus * ARINC 664 also known as Deterministic Ethernet * ARINC 825 Controller Area Network (CAN) * Common Airborne Instrumentation Systems (CAIS) * Cross Channel Data Link (CCDL) / Motor Controller Data Link (MCDL) * Ethernet * Fibre Channel * Firewire, IEEE 1394 * IRIG-106 PCM * MIL-STD-1553 * RS-232/RS-422/RS-485 * STANAG-3910 * Time-Triggered Protocol (TTP) Typically a bus monitor must listen-only on the bus and intercept a copy of the messages on the bus. In general a bus monitor never transmits on the monitored bus. Once the bus monitor has intercepted a message, the message is made available to the rest of the data acquisition system for subsequent recording and/or analysis. There are three classes of bus monitor: # Parser bus monitor # Snarfer bus monitor # Packetizer bus monitor == Parser bus monitor == Parser bus monitoring is also known as coherent monitoring or IRIG-106 Chapter 4 monitoring.〔(【引用サイトリンク】title=IRIG-106 Chapter 4 )〕 Parser bus monitors are suited to applications where the bus is highly active and only a few specific parameters of interest must be extracted. The parser bus monitor uses protocol tracking to identify and classify messages on the bus. From the identified messages of interest, specific parameters can be extracted from the captured messages. In order to ensure that coherency is achieved whereby all extracted parameters are from the same message instance, the parameters must be triple buffered with stale and skipped indicators. Optionally time tags can be added to each parsed message. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Bus monitoring」の詳細全文を読む スポンサード リンク
|